Hello Tom,
The other day i had a new user on machine and he bumped the keyboard and or mouse and placed a dot in the Gcode causing a unrecognized Gcode error when pressing Cycle Start.Had this happen a few times with me also. :)
Can Gcode area be blocked some how to keep this from happening? Maybe using one of the new split screens in version 4.34e and have one of the screens be set in a way so no input of the Gcode area can happen, this same screen would also be only for running the machine in "automatic" mode. Make sense?

Thanks again,
Troy

Hi Troy,

Sounds like a good idea.  Here is a patch for V4.34e that will allow the Screen Editor's GCode Edit control's Var setting to make it 0=Read Only or 1=Read/Write or -1=No Change.

You can also override this by right clicking on the GCode Editor and selecting "Allow Read/Write" or "Make Read Only"

Here is a patch:

http://dynomotion.com/Software/Patch/AddWriteProtectGCodeScreenwithVar1_V4343e/AddWriteProtectGCodeScreenwithVar1_V4343e.zip

Please let us know if that works for you.

Regards
TK

 

Hello Tom,
The other day i had a new user on machine and he bumped the keyboard and or mouse and placed a dot in the Gcode causing a unrecognized Gcode error when pressing Cycle Start.Had this happen a few times with me also. :)
Can Gcode area be blocked some how to keep this from happening? Maybe using one of the new split screens in version 4.34e and have one of the screens be set in a way so no input of the Gcode area can happen, this same screen would also be only for running the machine in "automatic" mode. Make sense?

Thanks again,
Troy

Hi Tom,
 This works great! :) Any way that the Right Click option can be eliminated?

On the same note, can another type of Var be added to not allow execution of Gcode, if either the on screen Start button is pushed or a physical push button?
Iam trying to lock the user into a default safe way of using control. :) So i made one of the 3 split screens as a general Input/manual mode of control. This has more of a industrial control approach.

Thanks again,
Troy

Hi Troy,

ok we added Var=2 tells forces the GCode Control to be Read Only with no overrride.

Your other request I don't really understand.  There may be some way you can implement that yourself.  You might remove the Start button from the screens where you don't want the User to be able to Start.  Screen Script can perform "Actions" such as setting or clearing a Virtual Bit.  So I believe if you manually add a line of script to your files such as:

Action:1;48;1;0;0;0;

This should set Virtual IO bit 48 when the screen is loaded.  Your external button might then check bit 48 in order to start.

The Screen editor probably needs some work to help facilitate this type of thing but it should still be functional.

Regards

TK

 

Hi Tom,
 This works great! :) Any way that the Right Click option can be eliminated?

On the same note, can another type of Var be added to not allow execution of Gcode, if either the on screen Start button is pushed or a physical push button?
Iam trying to lock the user into a default safe way of using control. :) So i made one of the 3 split screens as a general Input/manual mode of control. This has more of a industrial control approach.

Thanks again,
Troy

Hi Tom,
Awesome. :)

I have one screen set as just the GViewer with DROs, simulate check box, run button and MDI input. I have removed the Start button from screen, but was thinking if user accidentally pushed the physical Start button while in the Gviewer/Graphics screen, then mill machine would start running.

Thanks again, :)
Troy